Skip to content

Version Packages - #1841

Merged
yamcodes merged 1 commit into
devfrom
changeset-release/dev
Sep 11, 2026
Merged

Version Packages#1841
yamcodes merged 1 commit into
devfrom
changeset-release/dev

Conversation

@arkenv-bot

@arkenv-bot arkenv-bot Bot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to dev, this PR will be updated.

Releases

@arkenv/nextjs@0.1.6

Patch Changes

  • Widen the React peer dependency range #1833 230ed72 @yamcodes

    Allow @arkenv/nextjs to work with React 18.2.0 and later in the React 18 line, as well as every React 19 release, instead of requiring React 19.2.5. Install it alongside a supported React version, such as pnpm add @arkenv/nextjs react@^18.2.0.

@github-actions github-actions Bot added docs Adds or changes documentation, or acts as documentation in and of itself @arkenv/nextjs Issues or Pull Requests involving the Next.js integration for ArkEnv labels Sep 11, 2026
@pkg-pr-new

pkg-pr-new Bot commented Sep 11, 2026

Copy link
Copy Markdown

Open in StackBlitz

arkenv

npm i https://pkg.pr.new/arkenv@1841

@arkenv/build

npm i https://pkg.pr.new/@arkenv/build@1841

@arkenv/bun-plugin

npm i https://pkg.pr.new/@arkenv/bun-plugin@1841

@arkenv/cli

npm i https://pkg.pr.new/@arkenv/cli@1841

@arkenv/fumadocs-ui

npm i https://pkg.pr.new/@arkenv/fumadocs-ui@1841

@arkenv/nextjs

npm i https://pkg.pr.new/@arkenv/nextjs@1841

@arkenv/nuxt

npm i https://pkg.pr.new/@arkenv/nuxt@1841

@arkenv/vite-plugin

npm i https://pkg.pr.new/@arkenv/vite-plugin@1841

commit: 0ce06c6

@arkenv-bot

arkenv-bot Bot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor Author

📦 Bundle Size Report

Package Size Limit Diff Status
@arkenv/nextjs 1.32 kB 2.93 kB 0.0%
@arkenv/nextjs/shared 1.15 kB 1.46 kB 0.0%
@arkenv/nextjs/server 1.21 kB 1.95 kB 0.0%
@arkenv/nextjs/client 1.21 kB 1.95 kB 0.0%
@arkenv/nextjs/config 3.55 kB 3.91 kB 0.0%

All size limits passed!

@arkenv-bot
arkenv-bot Bot force-pushed the changeset-release/dev branch from 4c7caf5 to 0ce06c6 Compare September 11, 2026 19:52
@yamcodes
yamcodes merged commit d164500 into dev Sep 11, 2026
20 checks passed
@yamcodes
yamcodes deleted the changeset-release/dev branch September 11, 2026 20:55
yamcodes added a commit that referenced this pull request Sep 11, 2026
<!-- CURSOR_AGENT_PR_BODY_BEGIN -->
## Description

Restores examples sync after the `@arkenv/nextjs` `0.1.6` version bump
from Version Packages (#1841).

`pnpm sync:examples` updated:
- `examples/with-nextjs` and `examples/with-nextjs-strict`
`package.json` (`@arkenv/nextjs`: `^0.1.5` → `^0.1.6`)
- matching `package-lock.json` files for those examples

This fixes the failing `check-sync` job on the Sync `dev` → `main`
workflow.

Verified: `pnpm sync:examples:check` exits 0.

## Type of Change

- [x] Bug fix (non-breaking change which fixes an issue)

## Checklist

- [x] My code follows the code style of this project (double quotes,
tabs, no parameter reassignment).
- [x] I have written sentence-case imperative commits / PR title (e.g.
`Add support for custom error messages` - no `feat:`, no trailing
period, capitalized).
- [ ] I have added tests to cover my changes.
- [x] All new and existing tests passed.
- [ ] I have created a changeset using `pnpm changeset` (if this affects
a published package).

### For v0 (dev) PRs:
- [ ] **Forward-Porting**: (For maintainers) Has this change been
manually forward-ported to the `v1` branch?

No changeset needed — examples-only sync, no published package source
changes.


[sync-examples-check.log](https://cursor.com/agents/bc-6f754894-713f-40f5-b64d-41ff62cc6b6c/artifacts?path=%2Fopt%2Fcursor%2Fartifacts%2Fsync-examples-check.log)


<sub>To show artifacts inline, <a
href="https://cursor.com/dashboard/cloud-agents#my-pull-requests">enable</a>
in settings.</sub>
<!-- CURSOR_AGENT_PR_BODY_END -->

<div><a
href="https://cursor.com/agents/bc-6f754894-713f-40f5-b64d-41ff62cc6b6c?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-web-light.png"><img
alt="Open in Web" width="114" height="28"
src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a
href="https://cursor.com/background-agent?bcId=bc-6f754894-713f-40f5-b64d-41ff62cc6b6c&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img
alt="Open in Cursor" width="131" height="28"
src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div>

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

@arkenv/nextjs Issues or Pull Requests involving the Next.js integration for ArkEnv docs Adds or changes documentation, or acts as documentation in and of itself

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant